Online data market for automated plant growth input curve scripts

ABSTRACT

This disclosure describes techniques that facilitate the sale and exchange of plant growth systems to consumer plant growers. Particularly, a script offering system may act as an intermediary medium that allows merchants to advertise plant growth scripts to consumer plant growers via an electronic marketplace. In some examples, the script offering system may allow merchants to advertise plant growth scripts to consumer plant growers that have expressed an interest or need for a particular plant growth script. In other examples, the script offering system may allow a consumer plant grower to solicit merchant bids for the sale of plant growth script. A consumer plant grower may solicit bids for plant growth scripts that address specific needs identified via key word inputs or sensor data attributable to an existing plant growth operation that exhibits less than optimal plant growth.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.15/271,749, filed Sep. 21, 2016, which is incorporated by reference.

BACKGROUND

In a competitive marketplace, merchants of plant growth systems areoften required to go to great lengths to attract and retain consumerplant growers. Traditionally, merchants may rely on advertising andreputation to attract and retain consumers. More recently, merchants mayoffer special deals through advertising as a means of expanding theirmarket share. However, as an unintended consequence, consumers may beinundated with a plethora of advertisements from multiple merchants.Consumer plant growers may become frustrated by the number of availableoptions, and may choose to forgo the selection process. This mayultimately lead to lost sales revenue for competing merchants.

Presently, there is a need for a medium that allows merchants to targettheir advertisements towards consumer plant growers that have expresseda relevant need or interest in their plant growth systems. Further,there is also a need for a medium that allows consumer plant growers toaccess and solicit a network of merchants that address a consumer plantgrower's general and/or specific plant growing needs or interests.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items or features.

FIG. 1 illustrates a schematic view of an exemplary environment for thesale and exchange of automated plant growth scripts in an electronicmarketplace.

FIG. 2 illustrates a schematic view of an exemplary environment thatdescribes a plant grower device that interacts with a plant growthoperation controller to execute one or more automated plant groweractions.

FIG. 3 illustrates a block diagram of a script offering system thatfacilitates an interaction between a merchant that deals with plantgrowth scripts and a consumer plant grower.

FIG. 4 illustrates a block diagram of a merchant system associated witha merchant that offers plant growth scripts to consumer plant growers.

FIG. 5 illustrates a block diagram of plant grower system that mayexecute a plant growth script using sensor data received from a plantgrowth operation as inputs.

FIG. 6 illustrates a flow diagram for a process that describes a plantgrower system executing a plant growth script using sensor data receivedfrom a plant growth operation.

FIG. 7 illustrates is a flow diagram of a process that describes a plantgrower system generating a modified set of plant grower actions based onan indication that previously assigned plant grower actions have notbeen performed.

FIG. 8 illustrates is a flow diagram of a process that describes theplant grower system soliciting and receiving an update to a plant growthscript based on sub-optimal plant growth data.

FIG. 9 illustrates is a flow diagram of a process that describes a plantgrower system soliciting a script offering system to provide offers forplant growth scripts.

DETAILED DESCRIPTION

This disclosure describes techniques that facilitate the sale andexchange of plant growth systems to consumer plant growers.Particularly, this disclosure describes a script offering system thatmay act as an intermediary medium that allows merchants to advertiseplant growth scripts to consumer plant growers via an electronicmarketplace. In some examples, the script offering system may allowmerchants to advertise plant growth scripts to consumer plant growersthat have expressed an interest or need for a particular type of plantgrowth script. In other examples, the script offering system may allowconsumer plant growers to solicit merchants to bid for the sale of plantgrowth scripts. In some examples, a solicitation may include adescription of specific needs or interests. Alternatively, oradditionally, the solicitation may include sensor data from an existingplant growth operation that describes specific needs or interests.

The term “plant growth script” as used herein describes a computationalalgorithm that monitors a plant growth operation via one or moresensors. Sensor data from one or more sensors may include environmentaldata and image data that relates to a plant growth operation. In anon-limiting example, sensor data may include a measured lightintensity, a light spectrum, a proportion of nutrients and fertilizers,an amount of nutrients and fertilizers, an amount of water, and afrequency of a watering operation. Other sensor data may include thermalradiation, color, and temperature measurements of individual plants. Theplant growth scripts may also support conditional rules that trigger anevent based on sensor data. For example, if sensor data indicates thatlight intensity is less than a predetermined threshold, the plant growthscript may cause a change to the light intensity of lights within theplant growth operation. Further, conditional rules may trigger acompound event that is tied to Boolean logic. For example, if sensordata indicates than an amount of water dispensed over a predeterminedperiod of time is less than a predetermined threshold, the plant growthscript may cause an increase to the amount of water dispensed duringeach watering operation, as well as an increase to the frequency of thewatering operation.

In various examples, a plant grower system may execute the plant growthscripts. The plant grower system may be communicatively coupled to acontroller system of the plant growth operation. The controller systemmay capture sensor data from environmental sensor(s) and image capturingdevice(s) that monitor the plant growth operation, and transmit thesensor data to the plant grower system. The plant grower system may thenexecute a plant growth script, using the sensor data as an input, anddetermine plant grower action(s) that optimize plant growth. Plantgrower action(s) may include changing a light intensity or lightspectrum of existing lighting, changing an amount of water or afrequency of a watering operation, changing an amount of nutrients orfertilizer, or the ratio of nutrients to fertilizer used within a plantgrowth operation.

The plant grower system may transmit an indication of plant groweraction(s) to the controller system. In some examples, the controllersystem may automate the performance of plant grower action(s) within aplant growth operation. Automated plant grower action(s) may include theoperation and control of light intensity and light spectrum of anexisting lighting system, or control of the amount of water andfrequency of a watering operation.

The term “techniques,” as used herein, may refer to system(s),method(s), computer-readable instructions, module(s), algorithms,hardware logic, and/or operation(s) as permitted by the contextdescribed above and throughout the disclosure.

FIG. 1 illustrates a schematic view of a computing environment 100 thatdepicts the sale and exchange of plant growth script(s) 102 in anelectronic marketplace. The computing environment 100 may includemerchant(s) 104 that offer plant growth script(s) 102 to plant grower(s)106. The merchant(s) 104 may use a script offering system 108, as anintermediary medium, to present deals to plant grower(s) 106 via anelectronic marketplace. The deals may include an offer to purchase orlicense plant growth script(s) 102 that monitor a plant growthoperation. The plant growth script(s) 102 may determine one or moreplant grower action(s) that may optimize plant growth. The deals mayoffer a voucher 112 that may be redeemed for restricted or unrestrictedaccess to the plant growth script(s) 102. Restricted access may be basedon a predetermined period of time, or the duration of one or more plantlife cycle(s).

In the illustrated example, merchant(s) 104 may transmit offer data 110that is associated with plant growth script(s) 102 to the scriptoffering system 108. The offer data 110 may include a description of theplant growth script(s) 102 that includes the type of plants that theplant growth script(s) 102 intend to support, and the types of plantgrower actions that the plant growth script may use to optimize plantgrowth. Types of plant grower actions may include controlling lightintensity, light spectrum, an amount of water, and the frequency of awatering operation. The offer data 110 may also include a price forrestricted and/or unrestricted access to the plant growth script(s) 102,and conditions that govern the use of the plant growth script(s) 102.Conditions may include licensing agreement terms, a period of validity,and an availability of technical product support.

In the illustrated example, the script offering system 108 may present adeal that offers the plant growth script(s) 102 to plant grower(s) 106via the electronic market place. In one example, the deal may bepresented to all plant grower(s) 106 within the electronic market place.In another example, plant grower(s) 106 may be able to search for thedeal using an identifiably descriptive term. Further, plant grower(s)106 may be able to search for the deal by specifying a price range,licensing terms, a type of plant grower actions that the plant growthscript(s) 102 should accommodate, or the type of plants that the plantgrowth script(s) 102 should support. In some examples, rather thanoffering the deal for plant growth script(s) 102 to all plant grower(s)106, the script offering system 108 may present the deal to a subset ofplant grower(s) 106 based on consumer profile data. The consumer profiledata may be stored within the script offering system 108 and includedemographic data, a purchase history, or a history of online activity.

In the illustrated example, plant grower(s) 106 that purchase a deal forplant growth script(s) 102 may be able to obtain a voucher 112 from thescript offering system 108. The voucher 112 may be redeemable by themerchant(s) 104 in exchange for the plant growth script(s) 102 specifiedin the deal. The voucher 112 may be an electronic voucher or a tangiblevoucher. The script offering system 108 may accept a payment 114 fromthe plant grower(s) 106 in exchange for the voucher 112. In doing so,the script offering system 108 may transmit payment proceeds 116 to themerchant(s) 104 upon sale of the deal to the plant grower(s) 106. Insome examples, the payment proceeds 116 may comprise the value of thedeal less a commission retained by the script offering system 108 asconsideration for fulfillment of the sale. The commission may be a fixedvalue, a predetermined percentage of the deal value, or a combination ofboth.

In the illustrated example, the plant grower(s) 106 may present thevoucher 112 obtained from the script offering system 108 to themerchant(s) 104 for redemption. The merchant(s) 104, may verify anauthenticity and validity of the voucher 112 and in doing so, transmit acopy of the plant growth script(s) 102 specified in the voucher 112, toa plant grower system 118 associated with the plant grower(s) 106. Insome examples, the plant grower(s) 106 may present the voucher 112 at aphysical location associated with the merchant(s) 104. In otherexamples, the plant grower(s) 106 may electronically transmit thevoucher 112 to the merchant(s) 104. For example, the plant grower(s) 106may use a plant grower system 118 to communicate with the scriptoffering system 108 and the merchant system 120 via the one or morenetwork(s) 126. Similarly, the merchant(s) 104 may use the merchantsystem 120 to communicate with the script offering system 108 and theplant grower system 118. The plant grower system 118 and the merchantsystem 120 may be any sort of electronic device, such as a cellularphone, a smart phone, a tablet computer, an electronic reader, a mediaplayer, a gaming device, a personal computer (PC), a laptop computer,etc. Further, the one or more network(s) 126 may include public networkssuch as the Internet, private networks such as an institutional and/orpersonal intranet, or some combination of private and public networks.The one or more network(s) 126 can also include any type of wired and/orwireless network, including but not limited to local area networks(LANs), wide area networks (WANs), satellite networks, cable networks,Wi-Fi networks, WiMax networks, mobile communications networks (e.g.,3G, 4G, and so forth) or any combination thereof.

In the illustrated example, the script offering system 108 may operateon one or more distributed computing resource(s) 122. The one or moredistributed computing resource(s) 122 may include one or more computingdevice(s) 124 that operate in a cluster or other configuration to shareresource, balance load, increase performance, provide fail-over supportor redundancy, or for other purposes. Further, the one or more computingdevice(s) 124 may include one or more interfaces that enablecommunications with electronic device(s), such as the plant growersystem 118 and merchant system 120, via one or more network(s) 126.

FIG. 2 illustrates a schematic view of an exemplary environment of aplant grower system 202 that executes a plant growth script 204. Theplant grower system 202 may correspond to plant grower system 118. Theplant grower system 202 may receive sensor data 206 from environmentalsensor(s) 208 that monitor individual plants within a plant growthoperation 210. The sensor data 206 may include environmental data andimage data. In some examples, the environmental data may be temporallycorrelated, that is synchronized, with the image data. Environmentalsensor(s) 208 may capture environmental data associated with anindividual plant or a batch of plants. The environmental data may relateto a measured light intensity, light spectrum, a proportion of nutrientsand fertilizers, an amount of nutrients and fertilizers, an amount ofwater, a frequency of a watering operation, thermal radiation, color,and temperature. Environmental sensor(s) 208 may also monitor conditionsthat surround an individual plant and that apply to a batch of plants,generally. For example, a measurement of carbon dioxide intake or ameasurement of oxygen production may be used to determine a rate ofphotosynthesis. Environmental sensor(s) 208 may include, but are notlimited to, range-finding sensors, light intensity sensors, lightspectrum sensors, non-contact infra-red temperature sensors, thermalsensors, photoelectric sensors that detect changes in color, carbondioxide uptake sensors, and oxygen production sensors.

The plant grower system 202 may also include image capturing device(s)212 that capture visual and hyperspectral images of an individual plant,a grouping of plants, or a batch of plants. In some examples, the imagecapturing device(s) 212 may have a field of vision that focuses on anindividual plant, a group of individual plants, or a batch of plants. Insome examples, the image capturing device(s) 212 may capture images of asingle object, such as a plant, from at least two different locations,thereby creating at least two different lines of sight to points on theobject. The lines of sight may be further processed via a stereoscopicanalysis or structured light analysis to develop a three-dimensionalmodel of the plant.

The image capturing device(s) 212 may continuously capture visual andhyperspectral images of a plant, or batches of plants. Image capturingdevice(s) 212 may employ a time-lapse technique whereby the frequency atwhich image frames are captured is lower than that used to view thesequence. For example, an image of a plant may be captured once everyhour, then played back at 24 frames per second. The result is anapparent sequence of images that represent a 24-hour day being presentedin one second. Additionally, or alternatively, the image capturingdevice(s) 212 may capture visual and hyperspectral images of a plant orbatches of plants based on a triggering event. In a non-limitingexample, a triggering event may be based on a change in the relativeposition of an individual plant with its surroundings. In someinstances, the change in relative position may be based on an analysisof temporally sequential image data. In other instances, the change inrelative position may be based on motion detected by one or more motionsensors associated with the image capturing device(s) 212. In anothernon-limiting example, a triggering event may include an indication thatan environmental data-point has fallen below a predetermined threshold.For example, a triggering event may be determined by environmental dataindicating that the production of oxygen has fallen below a thresholdamount. Additionally, or alternatively, a triggering event may be basedon probability clustering of environmental data that relates toindividual plants, or batches of plants. For example, environmentaldata, and/or image data, may indicate a change in color of a single leafof an individual plant. In doing so, the change in color of a singleleaf may not be determined to be a triggering event. However, if theenvironmental data, and/or image data, indicates a presence of clustersof leaves with similar color changes, the clustering of color change maybe determined to be a triggering event.

The environmental sensor(s) 208 and the image capturing device(s) 212may be fixed installations within the plant growth operation 210. Inanother example, the environmental sensor(s) 208 and the image capturingdevice(s) 212 may be drone mounted to monitor the plant growth operation210.

In the illustrated example, the plant grower system 202 may receive theplant growth script 204 from a script offering system 214. The scriptoffering system 214 may correspond to the script offering system 108.Further, the plant grower system 202 may use the sensor data 206received from the plant growth operation 210 to determine plant groweraction(s) that may optimize plant growth. Plant grower action(s) mayinclude changing a light intensity or light spectrum of existinglighting within a plant growth operation, changing an amount of water ora frequency of a watering operation, changing an amount of nutrients orfertilizer, or the ratio of nutrients to fertilizer used within a plantgrowth operation. A plant grower action(s) data-set 216 may be generatedand transmitted to a controller system 218 of the plant growth operation210. In some examples, the controller system 218 may be configured toautomatically implement the plant grower action(s) received from theplant grower system 202. In other examples, the controller system 218may generate and send one or more alerts to an operator of the plantgrowth operation 210. The one or more alerts may include a listing ofthe plant grower action(s) with a tentative execution schedule. Thecontroller system 218 may operate on one or more computing device(s)that include one or more interfaces that enable communications withother electronic device(s) via one or more network(s) 220. The one ormore network(s) 220 may correspond to the one or more network(s) 126.

In the illustrated example, the plant grower system 202 may analysis thesensor data 206 and determine that plant growth progress is less thanoptimal, meaning that plant growth is progressing at a rate that is lessthan a predetermined threshold rate. In doing so, the plant growersystem 202 may generate and transmit a plant growth progress dataset 222to the script offering system 214 to solicit merchants to offer plantgrowth script 204 that may address the less than optimal plant growth.

FIG. 3 illustrates a block diagram of a script offering system 302 thatfacilitates an interaction between a merchant that deals with plantgrowth scripts and a consumer plant grower. The script offering system302 may present deals for plant growth scripts to consumer plant growerswithin an electronic marketplace. The deals may include an offer topurchase or license plant growth script(s) that monitor a plant growthoperation and determine one or more plant grower actions that mayoptimize plant growth.

In the illustrated example, the script offering system 302 may includeone or more processor(s) 304 that are operably connected to memory 306.In at least one example, the one or more processor(s) 304 may be one ormore central processing unit(s) (CPU), graphics processing unit(s)(GPU), both a CPU and GPU, or any other sort of processing unit(s). Eachof the one or more processor(s) 304 may have numerous arithmetic logicunits (ALUs) that perform arithmetic and logical operations as well asone or more control units (CUs) that extract instructions and storedcontent from processor cache memory, and then executes theseinstructions by calling on the ALUs, as necessary during programexecution. The one or more processor(s) 304 may also be responsible forexecuting all computer applications stored in the memory, which can beassociated with common types of volatile (RAM) and/or nonvolatile (ROM)memory.

In some examples, memory 306 may include system memory, which may bevolatile (such as RAM), non-volatile (such as ROM, flash memory, etc.)or some combination of the two. The memory may also include additionaldata storage devices (removable ad/or non-removable) such as, forexample, magnetic disks, optical disks, or tape.

The memory 306 may further include non-transitory computer-readablemedia, such as volatile and nonvolatile, removable and non-removablemedia implemented in any method or technology for storage ofinformation, such as computer readable instructions, data structures,program modules, or other data. System memory, removable storage andnon-removable storage are all examples of non-transitorycomputer-readable media. Examples of non-transitory computer-readablemedia include, but are not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other non-transitorymedium which can be used to store the desired information.

In the illustrated example, the memory 306 may include an operatingsystem 308, an authentication module 310, a script selection module 312,a transaction module 314, feedback module 316, a merchant accountdata-store 318, and a consumer profile data-store 320. The operatingsystem 308 may be any operating system capable of managing computerhardware and software resources.

In the illustrated example, the authentication module 310 may beconfigured to authenticate a merchant or consumer that accesses theelectronic marketplace associated with the script offering system 302.Authentication may be based on a device identifier used by the merchantor consumer when accessing the electronic marketplace. Alternatively, oradditionally, authentication may be based on entry of a username andpassword, or a biometric identifier.

In the illustrated example, the script selection module 312 may selectplant growth to advertise via the electronic marketplace. The selectionmay be based on advertising terms agreed upon with respective merchants.For example, merchants may offer payment for advertising plant growthscripts to a particular number of consumers or at particular times ofthe day. In other examples, the selection may be based on relative bidamounts offered by merchants to advertise through the electronicmarketplace. The processing of one or more merchant bids is discussed infurther detail below. Alternatively, or additionally, the selection maybe consumer-specific. For example, once a consumer has beenauthenticated via the authentication module 310, the script selectionmodule 312 may access profile data associated with the consumer and indoing so, select plant growth scripts that may align with knowninterests or consumer history. In a non-limiting example, the scriptselection module 312 may select a plant growth script for tomatoes for aconsumer with a history or interest in growing tomatoes. In otherexamples, the script selection module 312 may select plant growthscripts based on factors such as past purchase behavior, a geographiclocation of the plant grower, and environmental factors that relate to aplant grower's plant growth operation. Further, the script selectionmodule 312 may select plant growth scripts based on characteristics ofthe merchant offering the plant growth script. These characteristics mayinclude past purchase satisfaction ratings, or satisfaction ratingsassociated with the plant growth scripts themselves. Characteristics mayalso include correlated similarities between a merchant profile and aconsumer plant grower profile, such as a common geographic location.

In some instances, the script selection module 312 may also select plantgrowth scripts based on data uploaded by a particular plant grower. Forexample, a particular plant grower may be experiencing less than optimalplant growth. As result, the plant grower may upload data thatunderscores the progress of the plant growth operation. In doing so, thescript selection module 312 may transmit the data to one or moremerchants for the purpose of soliciting plant growth scripts that mayhelp rectify the plant grower's less than optimal plant growth. Thescript selection module 312 may then select one or more plant growthscripts offered by the solicited merchants for advertisement to theparticular plant grower, through the electronic marketplace.

In the illustrated example, the transaction module 314 may processpayments for a plant growth script that is purchased through theelectronic marketplace. The transaction module 314 may receive paymentsfrom financial accounts associated with consumer plant growers, andtransfer payment proceeds to financial accounts associated withmerchants. Further, the transaction module 314 may generate vouchersthat can be redeemed by a merchant for a plant growth script. Thetransaction module 314 may include a voucher component 322, a biddingcomponent 324, and a payment component 326.

The voucher component 322 may store redeemable vouchers for plant growthscripts purchased through the electronic marketplace. A redeemablevoucher may include information such as a voucher identifier, adescription of the plant growth script that is the subject of thevoucher, terms and conditions for redemption of the voucher, and otherpertinent information. A voucher identifier may be in the form ofnumbers, letters, symbols, or any combination thereof. Further, avoucher identifier may be an image, sound, or other piece ofcommunicable media recognized by the merchant or service provider thatis authenticating or validating the voucher. In a non-limiting example,a voucher may be generated by the voucher component 322 based oninformation received from a merchant. In this instance, a copy of thevoucher may be transmitted to the merchant system for the purpose ofverifying an authenticity of the voucher at a time of redemption. Inanother non-limiting example, a voucher may be generated by the merchantand sent to the voucher component 322 of the script offering system 302.In this example, the voucher may be issued to consumer plant growers ata time of sale, and an authenticity of the voucher may be verified bythe originating merchant at a time of redemption.

The bidding component 324 may receive and process one or more bids frommerchants to advertise plant growth scripts through the electronicmarketplace. A bid may include a bid amount and conditions associatedwith fulfillment of a transaction for a plant growth script. The biddingcomponent 324 may structure a bidding system according to any knownsystem or otherwise. For example, a bid amount may correspond tofinancial remuneration that a merchant is willing to accept asconsideration for sale of a plant growth script. The bidding component324 may automatically select a winning bid based on a most favorable bidamount. That is, lowest cost to the plant grower. In a non-limitingexample, a bidding arrangement may include a submission of a bid with anominal bid amount, a minimum bid amount, and a condition whereby thenominal bid amount decreases to a bid amount lower than the next lowestbid amount, up to the minimum bid amount. In some examples, the criteriafor selecting a winning bid may be based on consumer input that issourced from the consumer profile data-store 320. For example, a winningbid may be selected based on preferred characteristics such as feedbackstar-rating, favorable redemption conditions and an availability oftechnical support.

The payment component 326 may receive payments from financial accountsassociated with consumer plant growers, and transfer payment proceeds tofinancial accounts associated with merchants. The payment component 326may accept many different payment types including electronic paymenttypes (EPT) (e.g., credit cards, debit cards, stored value cards, etc.)and/or other payment types (e.g., cash, personal checks, money orders,etc.) in exchange for the voucher.

In the illustrated example, the feedback module 316 may allow consumersto provide feedback. Feedback may include a rating, comment, or reviewof a plant growth script. The feedback module 316 may prompt a consumerto provide feedback about a plant growth script, a point in time afterthe consumer has redeemed the voucher associated with the plant growthscript. The feedback module 316 may also present special offers toincentivize the consumer to provide feedback.

In some examples, the consumer may provide a rating for a plant growthscript. The feedback module 316 may aggregate the rating provided by theconsumer with other ratings provided by other consumers for the sameplant growth script. Thus, when a different consumer requests to view adescription of the plant growth script, the script offering system 302may present a description of the plant growth script along with theaggregated rating. Further, the feedback module 316 may also compare anaggregated rating provided by consumers for a particular plant growthscript, with an aggregated rating of a same genre of plant growthscripts that are offered by multiple merchants. For example, a consumermay search for a plant growth script for growing mangoes. In doing so,the script selection module 312 may present a particular plant growthscript with a three out of five-star rating that is offered by merchant‘A’. The script selection module 312 may also present a general two-starrating for mango plant growth scripts that are offered by merchants A,B, C, D, and E. In other words, even though a three-star rating for amango plant growth script may appear mediocre on a five-star scale, therating can be perceived as above average when compared to the two-starrating that is based on aggregated offerings of merchants A, B, C, D,and E.

In the illustrated example, the merchant account data-store 318 mayinclude various types of identifying information of one or moremerchants that offer plant growth scripts on the electronic marketplace.In a non-limiting example, the identifying information may include aname of the merchant, an identifier number or code associated with amerchant, an address of a merchant, and a location of a merchant. Insome examples, the merchant account record may also include satisfactionratings and feedback associated with previous sales or licenses made toconsumer plant growers. Further, the merchant account record may alsoinclude financial account information associated with the merchant. Thefinancial account information may include account numbers, routingnumbers, passwords or electronic communication protocols that arerequired to access the financial account. The financial account may bethe target or end point for payment proceeds from a consumer to themerchant.

In the illustrated example, the consumer profile data-store 320 mayinclude various types of identifying information of consumers thatsearch for plant growth scripts via the electronic marketplace. Theconsumer profile data-store 320 may develop a consumer profile for plantgrowers based on plant growth script purchase history, plant groweronline activity detected within the plant growth marketplace. Thepurchase history may include purchase information for one or morepurchase transactions, such as an identity of the plant grower, identitydata associated with the merchant, description of each item, a quantityof each item purchases, and a price paid for each item purchased.Consumer activity may include information on other actions of the plantgrower with each of the one or more merchants, the service provider, orany combination thereof. The consumer activity may include informationrelating to a search history of the consumer within the electronicmarketplace, one or more advertisement click-through histories of theconsumer, information on one or more item reviews, one or more itemratings, one or more item recommendations, or other online activitiesthat may be attributed to the consumer.

In the illustrated example, the script offering system 302 may furtherinclude input/output interface(s) 328. The input/output interface(s) 328may include any type of output interface known in the art, such as adisplay (e.g., a liquid crystal display), speakers, a vibratingmechanism, or a tactile feedback mechanism. Input/output interface(s)328 also include ports for one or more peripheral devices, such asheadphones, peripheral speakers, or a peripheral display. Further, theinput/output interface(s) 328 may further include a camera, amicrophone, a keyboard/keypad, or a touch-sensitive display. Akeyboard/keypad may be a push button numerical dialing pad (such as on atypical telecommunication device), a multi-key keyboard (such as aconventional QWERTY keyboard), or one or more other types of keys orbuttons, and may also include a joystick-like controller and/ordesignated navigation buttons, or the like.

In the illustrated example, the script offering system 302 may includeone or more network interface(s) 330. The one or more networkinterface(s) 330 may include any sort of transceiver known in the art.For example, the one or more network interface(s) 330 may include aradio transceiver that performs the function of transmitting andreceiving radio frequency communications via an antenna. In addition,the one or more network interface(s) 330 may also include a wirelesscommunication transceiver and a near field antenna for communicatingover unlicensed wireless Internet Protocol (IP) networks, such as localwireless data networks and personal area networks (e.g., Bluetooth ornear field communication (NFC) networks). Further, the one or morenetwork interface(s) 330 may include wired communication components,such as an Ethernet port or a Universal Serial Bus (USB).

FIG. 4 illustrates a block diagram of a merchant system 402 associatedwith a merchant that offers plant growth scripts to consumer plantgrowers. The merchant system 402 may correspond to merchant system 120.In the illustrated example, the merchant system 402 may include one ormore processor(s) 404 operably connected to memory 406. The one or moreprocessor(s) 404 may correspond to the one or more processor(s) 304, andthe memory 406 may correspond to the memory 306.

In the illustrated example, the memory 406 may include an operatingsystem 408, a subscription module 410, a voucher module 412, atransaction module 414, a data-store 416, and a user interface 418. Theoperating system 408 may be any operating system capable of managingcomputer hardware and software resources.

In the illustrated example, the subscription module 410 may managesubscriptions of plant growth scripts associated with plant growers thatchoose to license rather than purchase plant growth scripts. Thesubscription module 410 may limit plant grower systems' access to plantgrowth scripts based on terms of respective licensing agreements. Insome instances, access may be limited to a predetermined time interval,or one or more plant life cycles. In some instances, the subscriptionmodule 410 may transmit notifications that alert plant grower systemsthat a subscription period is to expire.

Further, the subscription module 410 may cause script updates to betransmitted to plant grower systems based on terms of respectivelicensing agreements. In some examples, script updates may bedynamically sent to plant grower systems, soon after the plant growthscripts become available to a merchant. In other examples, scriptupdates may be selectively transferred to plant grower systems based onthe plant grower system's percentage completion of the previous versionof the plant growth script. The subscription module 410 may solicit anindication from a plant grower system that clarifies a percentagecompletion of the previous version of plant growth script. Uponreceiving a response from the plant grower system, and upon determiningthat the percentage completion is less than a predetermined percentagethreshold, the subscription module 410 may transmit the script update tothe plant grower system. In other words, if a plant grower has completeda significant portion of a plant growth script, a script update maycause harm to the plant growth operation. Thus, in some cases, it may bein the best interest of the plant grower for the subscription module 410to withhold script updates until the plant life cycle is complete.

In the illustrated example, the voucher module 412 may generateredeemable vouchers that can be exchanged for access to plant growthscripts. The vouchers may be sent to the script offering system 302 forissuance to consumer plant growers at a time of sale through theelectronic marketplace. The vouchers may include information such as avoucher identifier, a description of the plant growth script that is thesubject of the voucher, terms and conditions of redemption of thevoucher, and other pertinent information. A voucher identifier may be inthe form of numbers, letters, symbols, or any combination thereof.Further, a voucher identifier may be an image, sound, or other piece ofcommunicable media recognized by the merchant or service provider thatis authenticating or validating the voucher. In an alternativeembodiment, the voucher module 412 may receive vouchers generated by avoucher component 322 of the script offering system 302. This allows amerchant to verify an authenticity of a voucher generated by the scriptoffering system 302 at a time of redemption by the consumer plantgrower.

In the illustrated example, the transaction module 414 may verifytransactions implemented by the script offering system with consumerplant growers, on behalf of the merchant. The transaction module 414 mayinclude a payment component 420, and a redemption verification component422. The payment component 420 may receive an indication that paymentproceeds from the script offering system 302 have been transferred to amerchant in relation to the sale or licensing of a plant growth script.In some examples, the payment component 420 may receive an indicationthat payment proceeds have been transferred to a financial accountassociated with the merchant. In other examples, the payment component420 may receive an indication that payment has been sent to the merchantin the form of cash, personal check money order as consideration for thesale or licensing of the plant growth script.

The redemption verification component 422 may verify an authenticity ofa request to redeem a voucher. In some examples, the redemptionverification component 422 may determine that a redemption request isvalid when a voucher identifier associated with a voucher issued by thescript offering system, match designated confirmation credentialsassociated with the redemption of that same voucher. In at least oneexample, the redemption request may also need to meet one or moreadditional criteria in order to be considered valid. For example, theredemption verification component 422 may verify that the voucher hasnot been previously redeemed, and that the voucher has not expired. Insome examples, verification data used to verify an authenticity of avoucher may include text, a picture, a sound, a video, or a hapticresponse, any of which may be required as part of a redemption process.

In the illustrated example, the data-store 416 may store a record ofredeemable vouchers generated by the voucher module 412, or receivedfrom the script offering system 302. The record may include informationsuch as a voucher identifier, a description of the plant growth scriptthat is the subject of the voucher, terms and conditions for redemptionof the voucher, and other pertinent information. Further, the data-store416 may also store the plant growth scripts that are marketed via theelectronic marketplace, for issuance to consumer plant growers.

In the illustrated example, the user interface 418 may be presented on adisplay device that interfaces with the merchant system 402 via theinput/output interface(s) 424. The user interface 418 may present amerchant to receive alerts sent from the script offering system 302. Thealerts may include a notification of a sale of a voucher associated witha plant growth script, and/or a request or receipt of voucherinformation. Further, the user interface 418 may provide a merchant withan option to generate a voucher, and transmit the voucher to the scriptoffering system for issuance to consumer plant growers. Further, theuser interface 418 may also allow a merchant to generate a bid toadvertise one or more plant growth scripts via the electronicmarketplace.

In the illustrated example, the merchant system 402 may includeinput/output interface(s) 424 and network interface(s) 426. Theinput/output interface(s) 424 and the network interface(s) 426 maycorrespond to the input/output interface(s) 328 and the networkinterface(s) 330 respectively.

FIG. 5 illustrates a block diagram of a plant grower system 502 that mayexecute a plant growth script using sensor data received from a plantgrowth operation as inputs. In doing so, the plant grower system 502 maydetermine one or more plant grower actions that optimize plant growth ofassociated with the plant growth operation. The plant grower system 502may correspond to plant grower system 118 and 202. In the illustratedexample, the plant grower system 502 may include one or moreprocessor(s) 504 operably connected to memory 506. The one or moreprocessor(s) 504 may correspond to the one or more processor(s) 304 and404, and the memory 506 may correspond to the memory 306 and 406.

In the illustrated example, the memory 506 may include an operatingsystem 508, a data collector module 510, a script processing module 512,a redemption module 514, a data-store 516, and a user interface 518. Theoperating system 508 may be any operating system capable of managingcomputer hardware and software resources.

In the illustrated example, the data collector module 510 may aggregatethe sensor data received from the plant growth operation to generateinputs for the plant growth script. The sensor data may include ameasured light intensity, a light spectrum, a portion of nutrients andfertilizers, an amount of nutrients and fertilizers, an amount of water,and a frequency of a watering operation. Other sensor data may includethermal radiation, color, and temperature measurements of individualplants.

In the illustrated example, the script processing module 512 may executethe plant growth script using, as inputs, the processed data from thedata collector module 510. In some examples, the script processingmodule 512 may determine a progress metric based at least in part on thesensor data. The progress metric may quantify progress of plant growthwithin the plant growth operation relative to milestones predicted bythe plant growth script. The progress metric may be represented as aninteger on a predetermined scale that reflects optimal growth as amedium point on the scale, less than optimal growth on a numerically lowpoint on the scale, and advanced growth on a numerically high point onthe scale. In other examples, the progress metric may be represented asa color chart, that varies in tone and shade between red and green toreflect less than optimal growth and more than optimal growth,respectively.

In a non-limiting example, sensor data may indicate that at a particularpoint in time during the plant life cycle, one or more plant(s) withinthe plant growth operation are at an early stage of development based ontheir size, shape, or color. At the same time, the plant growth scriptmay determine that the one or more plant(s) should have reached aparticular milestone that reflects a more advanced stage of development,based on an expected threshold size, shape, or color. Accordingly, theplant growth script may quantify a progress metric that reflects lessthan optimal growth and further transmit an alert to a plant growerindicating the same. Alternatively, if sensor data indicates that plantgrowth has timely reached an expected milestone, the script processingmodule 512 may quantify a progress metric that reflects the same, andalso transmit an alert that notifies the plant grower that one or moreplant(s) have timely reached an expected milestone. The alert mayfurther indicate that plant growth progress is at an optimal level.

In the illustrated example, the redemption module 514 may manage theredemption of vouchers for plant growth scripts purchased or licensed bya plant grower. In one non-limiting example, the redemption module 514may cause a voucher to be displayed by the plant grower system 502 for apredetermined amount of time, after which the voucher may expire. Themerchant may verify an authenticity and validity of the voucher byviewing displayed voucher. In an alternative embodiment, the redemptionmodule 514 may transmit the voucher electronically to the merchant. Indoing so, the merchant may verify an authenticity and validity of thevoucher, and then send to the plant grower system 502, the plant growthscript that is the subject of the voucher.

In the illustrated example, the data-store 516 may store acquiredvouchers for plant growth scripts acquired via the electronicmarketplace. The acquired vouchers may be retained within the data-store516 while they remain valid. That is, the acquired vouchers may remainwithin the data-store 516 until they expire, or until they are redeemedby a merchant. Further, the data-store 516 may store data relating tothe plant growth scripts received from merchants. The data may includeplant growth script execution files and result files. In some examples,the plant growth script execution files may be stored indefinitelywithin the data-store 516. In other examples, the plant growth scriptexecution files may be stored for a predetermined period of time that isgoverned by an access licensing agreement between the merchant and theplant grower.

In the illustrated example, the user interface 518 may be configured todisplay notifications that alert consumer plant growers of the progressof a plant growth operation with respect to an expected stage of plantgrowth based on the plant growth script. In some examples, the alert mayindicate that the progress observed by one or more sensors of the plantgrowth operation may be less than expected based on the plant growthscript. Alternatively, the alert may indicate that plant growthassociated with the plant growth operation is at an expected stage or anadvanced stage of completion. In various examples, the user interface518 may provide a means for a plant grower to upload a results filegenerated by the plant growth script to the script offering system. Thepurpose of doing so allows a plant grower to solicit plant growthscripts from merchants, based on data associated with a plant growthoperation. Additionally, or alternatively, the results file may alsoinclude a comparison of plant growth progress relative to the stage ofcompletion of the plant growth script. In some examples, the userinterface 518 may also provide a means for a plant grower to request andselect bids for plant growth scripts from merchants via the scriptoffering system. The user interface 518 may also allow plant growers tospecify underlying conditions that solicited bids must meet. In anon-limiting example, the underlying conditions may include a preferredlicensing duration, a minimum satisfaction rating of a plant growthscript or merchant, or a request for a plant growth script for aparticular plant species.

In the illustrated example, the plant grower system 502 may includeinput/output interface(s) 520 and network interface(s) 522. Theinput/output interface(s) 520 and the network interface(s) 522 maycorrespond to the input/output interface(s) 328 and 424, and the networkinterface(s) 330 and 426 respectively.

FIG. 6 illustrates a flow diagram for a process that describes a plantgrower system executing a plant growth script using sensor data receivedfrom a plant growth operation. The plant growth script may be used todetermine one or more plant grower actions that optimize plant growth ofa plant growth operation. At 602, the plant grower system may receivesensor data from one or more sensors of a plant growth operation. Theone or more sensors may include image capturing devices andenvironmental sensors. The environmental sensors may include, but arenot limited to, non-contact infra-red temperature sensors, thermalsensors, photoelectric sensors that detect changes in color, carbondioxide uptake sensors, and oxygen production sensors.

At 604, the plant grower system may execute a plant growth script todetermine plant growth progress of the plant growth operation. The plantgrowth script may use sensor data as an input to quantify a progressmetric that quantifies progress of plant growth at a particular point intime. The progress metric may be based on a comparison of a size, shape,or color of one or more plant(s) within the plant growth operation, withan expected size, shape, or color milestone that is based on the pointin time that the sensor data is received.

At 606, the plant grower system may recommend one or more plant groweractions to optimize plant growth, based at least in part on the progressmetric. For example, if the sensor data indicates a less than optimallevel of plant growth, the one or more plant grower actions may includechanging a light intensity or light spectrum of existing lighting,changing an amount of water or a frequency of a watering operation,changing an amount of nutrients or fertilizer, or the ratio of nutrientsto fertilizer used within the plant growth operation.

At 608, the plant grower system may determine that the one or more plantgrower actions are automated by a controller system of the plant growthoperation. In doing so, the plant grower system may transmit a data-setto the controller system that includes parameters for the controllersystem to implement one or more automated plant grower actions.Automated plant grower actions may include, but are not limited to,controlling and operating light intensity, light spectrum of existinglighting, and controlling and operating an amount of water or wateringfrequency of a watering operation.

At 610, the plant grower system may determine that the one or more plantgrower actions are not automated by a controller system of the plantgrowth operation. Thus, a plant grower may be required to manuallyschedule or perform the one or more plant grower actions. Thus, theplant grower system may transmit an indication to a client device of aplant grower that describes the one or more plant grower action(s). Insome examples, the indication may also include an alert that notifiesthe plant grower that plant growth is at a less than optimal level, anoptimal level, or an advanced level.

FIG. 7 illustrates is a flow diagram of a process that describes a plantgrower system generating a modified set of plant grower actions based onan indication that previously assigned plant grower actions have notbeen performed. At 702, the plant grower system may receive sensor datafrom one or more sensors that monitor a plant growth operation. Thesensor data may include measured light intensity, a light spectrum, aproportion of nutrients and fertilizers, an amount of nutrients andfertilizer, an amount of water, and a frequency of a watering operation.

At 704, the plant grower system may determine whether previouslyassigned plant grower actions have been performed, based at least inpart on the sensor data. In some examples, the plant grower system mayreceive an indication from a controller system of the plant growthoperation that an automated plant grower action has been performed.Additionally, or alternatively, the plant grower system may processsensor data to observe performance of the plant grower action. In onenon-limiting example, light sensors may measure light intensity or lightspectrum at a particular point in time. The plant grower system may thencompare the measured data with plant grower actions that mandate aparticular light intensity or light spectrum. In another example,processed image sensor data may indicate the performance of other plantgrower actions, such as an amount of water and a frequency of a wateringoperation.

At 706, the plant grower system may determine that previously assignedplant grower actions have not been performed. Continuing with the aboveexample, the plant grower system may determine that the measure lightintensity or light spectrum does not match those prescribed by the plantgrower actions. In doing so, the plant grower system may determine amodified set of plant grower actions. The modified set of plant groweractions may compensate for the time lapse from when the previouslyassigned grower actions were intended to be performed. Alternatively,the plant grower system may determine that previously assigned plantgrower actions have been performed, based on the sensor data. In doingso, the plant grower system may continue to monitor progress of theplant growth operation.

At 708, the plant grower system may transmit an alert to a client deviceof the plant grower along with the modified set of plant grower actions.The alert may indicate that previously assigned plant grower actionswere not performed, and that a modified set of plant grower actions hasbeen assigned. In some examples, if the plant grower actions wereintended to be automated by a controller system of the plant growthoperation, data associated with the modified set of plant grower actionsmay be transmitted to the controller system. At the same time, an alertmay be sent to the client device of the plant grower indicating that oneor more automated plant grower action(s) were not performed, and that amodified set of plant grower actions has been assigned to the controllersystem.

FIG. 8 illustrates is a flow diagram of a process that describes theplant grower system soliciting and receiving an update to a plant growthscript based on sub-optimal plant growth data. In some examples, thesolicitation for an update to the plant growth script occur directlybetween the plant grower and the merchant that provided the plant growthscript, or via the script offering system as an intermediary. At 802,the plant growth system may determine that a plant growth operation maybe experiencing less than optimal plant growth. In some examples, theindication may be based on the size, shape, or color of one or moreplant(s) within the plant growth operation, relative to expectedmilestones predicted by a plant growth script.

At 804, the plant grower system may transmit an alert to the merchantthat provided the plant growth script indicating less than optimal plantgrowth, and soliciting an update to the plant growth script. In someexamples, the plant grower system may also transmit a plant growthprogress data-set that includes sensor data from the plant growthoperation over a predetermined period of time. In some examples, theplant grower system may transmit the alert to the merchant via thescript offering system as an intermediary. A benefit of doing so may befor the script offering system to timely redirect the alert to an entityother than the merchant that may be responsible for developing updatesto plant growth scripts.

At 806, the plant grower system may receive an update for the plantgrowth script. In doing, the plant grower system may execute the updateto the plant growth script to determine a set of modified plant groweractions.

FIG. 9 illustrates a flow diagram of a process that describes a plantgrower system soliciting a script offering system to provide offers forplant growth scripts. In some examples, the script offering system mayshare the solicitation with several merchants that participate in theelectronic marketplace, with the aim of allowing each merchant to offera bid in response to the solicitation. At 902, the plant grower systemmay transmit a solicitation to the script offering system that requestsoffers for plant growth script(s). The solicitation may include adescription of a particular plant species that is being grown at theplant growth operation. Further, the solicitation may include one ormore conditions that solicited bids must meet. For example, the one ormore conditions may include a preference to purchase a script ratherthan licensing a script. Alternatively, the one or more conditions mayinclude a preference to license a script, along with a preferredlicensing duration. Other conditions may include a preferred pricerange, or a minimum satisfaction rating of a plant growth script or themerchant that offers the plant growth script.

In some examples, the solicitation may include a plant growth progressdata-set that includes sensor data from a current plant growth operationover a predetermined period of time. In doing so, the solicitation mayinclude a condition that merchant offers should address optimizing plantgrowth of the current plant growth operation, based on the plant growthprogress data set.

At 904, the plant grower system may receive one or more bids fromseveral merchants that offer plant growth scripts, based at least inpart on the one or more conditions. Each bid may include a bid amountand merchant conditions associated with fulfillment of a transaction fora plant growth script. The bid amount may correspond to financialremuneration that a merchant is willing to accept as consideration forsale of a plant growth script.

At 906, the plant grower system may select a winning bid for an offer ofa plant growth script. In some examples, the winning bid may be selectedmanually by a plant grower, via a user interface of the plant growersystem. In other examples, the winning bid may be automatically selectedby the plant grower system, based on one or more criteria such as thelowest cost to the plant grower, fulfilment of plant grower conditions,favorable merchant redemption conditions, and a minimum feedback rating.Favorable redemption conditions may include the duration of a licensingagreement, the availability of technical support, and the provision ofscript updates during the term of the licensing agreement. A plantgrower may configure the plant grower system to prioritize selection ofa winning bid for a plant growth script based on favorable redemptionconditions relative to one another and also relative to a bid amount. Inother words, a plant grower may prioritize fulfillment of all plantgrower conditions and a provision of technical support above a lowestcost to the plant grower. In doing so, the plant grower system mayautomatically select a more expensive plant growth script based on thatselection criteria.

CONCLUSION

Although the subject matter has been described in language specific tofeatures and methodological acts, it is to be understood that thesubject matter defined in the appended claims is not necessarily limitedto the specific features or acts described herein. Rather, the specificfeatures and acts are disclosed as exemplary forms of implementing theclaims.

What is claimed:
 1. A computer-implemented method, comprising:receiving, from a plant grower system, by an electronic plant growthscript marketplace, (i) first data indicating that a plant managed bythe plant grower system according to a first plant growth script isexperiencing growth that is below a threshold growth level and (ii) afirst request for an additional plant growth script that is configuredto address the growth that is below the threshold growth level; inresponse to receiving (i) the first data indicating that the plantmanaged by the plant grower system according to the first plant growthscript is experiencing the growth that is below the threshold growthlevel and (ii) the first request for the additional plant growth scriptthat is configured to address the growth that is below the thresholdgrowth level, transmitting, to a merchant system, by the electronicplant growth script marketplace, a second request for a given plantgrowth script that is configured to address the growth that is below thethreshold growth level; in response to the second request for the givenplant growth script that is configured to address the growth that isbelow the threshold growth level, receiving, from the merchant system,by the electronic plant growth script marketplace, a second plant growthscript that is configured to address the growth that is below thethreshold growth level; and providing, to the plant grower system, foroutput by the electronic plant growth script marketplace, the secondplant growth script and second data indicating that the second plantgrowth script is configured to address the growth that is below thethreshold growth level.
 2. The method of claim 1, wherein the firstrequest for the additional plant growth script comprises sensor datagenerated by one or more sensors that monitor the plant.
 3. The methodof claim 2, wherein the sensor data comprises at least one ofrange-finding data, light intensity data, light spectrum data,non-contact infra-red temperature data, thermal data, image data,photoelectric data that indicates changes in color, carbon dioxideuptake data, and oxygen production data.
 4. The method of claim 1,wherein the plant growth script in the first plant growth script, or inthe given plant growth script, or in the second plant growth scriptcomprises a computational algorithm that monitors the plant by analyzingsensor data generated by one or more sensors and supports conditionalrules that trigger events based on the sensor data.
 5. The method ofclaim 4, wherein the trigger events include at least one of changing alight intensity or a light spectrum of existing lighting illuminatingthe plant, changing an amount of water or a frequency of the waterprovided to the plant, changing an amount of nutrients or fertilizerprovided to the plant, or changing a ratio of the nutrients to thefertilizer provided to the plant.
 6. The method of claim 1, wherein thefirst data indicating that the plant managed by the plant grower systemaccording to the first plant growth script is experiencing the growththat is below the threshold growth level comprises data indicating thatsize, shape, or color of the plant does not meet a particular size,shape, or color specified by the first plant growth script.
 7. Themethod of claim 1, wherein the first request for the additional plantgrowth script that is configured to address the growth that is below thethreshold growth level comprises a request to license the additionalplant growth script for a particular duration.
 8. A system, comprising:one or more processors; and memory including a plurality ofcomputer-executable components that are executable by the one or moreprocessors to perform a plurality of acts, the plurality of actscomprising: receiving, from a plant grower system, by an electronicplant growth script marketplace, (i) first data indicating that a plantmanaged by the plant grower system according to a first plant growthscript is experiencing growth that is below a threshold growth level and(ii) a first request for an additional plant growth script that isconfigured to address the growth that is below the threshold growthlevel; in response to receiving (i) the first data indicating that theplant managed by the plant grower system according to the first plantgrowth script is experiencing the growth that is below the thresholdgrowth level and (ii) the first request for the additional plant growthscript that is configured to address the growth that is below thethreshold growth level, transmitting, to a merchant system, by theelectronic plant growth script marketplace, a second request for a givenplant growth script that is configured to address the growth that isbelow the threshold growth level; in response to the second request forthe given plant growth script that is configured to address the growththat is below the threshold growth level, receiving, from the merchantsystem, by the electronic plant growth script marketplace, a secondplant growth script that is configured to address the growth that isbelow the threshold growth level; and providing, to the plant growersystem, for output by the electronic plant growth script marketplace,the second plant growth script and second data indicating that thesecond plant growth script is configured to address the growth that isbelow the threshold growth level.
 9. The system of claim 8, wherein thefirst request for the additional plant growth script comprises sensordata generated by one or more sensors that monitor the plant.
 10. Thesystem of claim 9, wherein the sensor data comprises at least one ofrange-finding data, light intensity data, light spectrum data,non-contact infra-red temperature data, thermal data, image data,photoelectric data that indicates changes in color, carbon dioxideuptake data, and oxygen production data.
 11. The system of claim 8,wherein the plant growth script in the first plant growth script, or inthe given plant growth script, or in the second plant growth scriptcomprises a computational algorithm that monitors the plant by analyzingsensor data generated by one or more sensors and supports conditionalrules that trigger events based on the sensor data.
 12. The system ofclaim 11, wherein the trigger events include at least one of changing alight intensity or a light spectrum of existing lighting illuminatingthe plant, changing an amount of water or a frequency of the waterprovided to the plant, changing an amount of nutrients or fertilizerprovided to the plant, or changing a ratio of the nutrients to thefertilizer provided to the plant.
 13. The system of claim 8, wherein thefirst data indicating that the plant managed by the plant grower systemaccording to the first plant growth script is experiencing the growththat is below the threshold growth level comprises data indicating thatsize, shape, or color of the plant does not meet a particular size,shape, or color specified by the first plant growth script.
 14. Thesystem of claim 8, wherein the first request for the additional plantgrowth script that is configured to address the growth that is below thethreshold growth level comprises a request to license the additionalplant growth script for a particular duration.
 15. One or morenon-transitory computer-readable media storing computer-executableinstructions that upon execution cause one or more computers to performacts comprising: receiving, from a plant grower system, by an electronicplant growth script marketplace, (i) first data indicating that a plantmanaged by the plant grower system according to a first plant growthscript is experiencing growth that is below a threshold growth level and(ii) a first request for an additional plant growth script that isconfigured to address the growth that is below the threshold growthlevel; in response to receiving (i) the first data indicating that theplant managed by the plant grower system according to the first plantgrowth script is experiencing the growth that is below the thresholdgrowth level and (ii) the first request for the additional plant growthscript that is configured to address the growth that is below thethreshold growth level, transmitting, to a merchant system, by theelectronic plant growth script marketplace, a second request for a givenplant growth script that is configured to address the growth that isbelow the threshold growth level; in response to the second request forthe given plant growth script that is configured to address the growththat is below the threshold growth level, receiving, from the merchantsystem, by the electronic plant growth script marketplace, a secondplant growth script that is configured to address the growth that isbelow the threshold growth level; and providing, to the plant growersystem, for output by the electronic plant growth script marketplace,the second plant growth script and second data indicating that thesecond plant growth script is configured to address the growth that isbelow the threshold growth level.
 16. The media of claim 15, wherein thefirst request for the additional plant growth script comprises sensordata generated by one or more sensors that monitor the plant.
 17. Themedia of claim 16, wherein the sensor data comprises at least one ofrange-finding data, light intensity data, light spectrum data,non-contact infra-red temperature data, thermal data, image data,photoelectric data that indicates changes in color, carbon dioxideuptake data, and oxygen production data.
 18. The media of claim 15,wherein the plant growth script in the first plant growth script, or inthe given plant growth script, or in the second plant growth scriptcomprises a computational algorithm that monitors the plant by analyzingsensor data generated by one or more sensors and supports conditionalrules that trigger events based on the sensor data.
 19. The media ofclaim 15, wherein the first data indicating that the plant managed bythe plant grower system according to the first plant growth script isexperiencing the growth that is below the threshold growth levelcomprises data indicating that size, shape, or color of the plant doesnot meet a particular size, shape, or color specified by the first plantgrowth script.
 20. The media of claim 15, wherein the first request forthe additional plant growth script that is configured to address thegrowth that is below the threshold growth level comprises a request tolicense the additional plant growth script for a particular duration.